feat: improved embed navigation APIs - #9866

Two navigation edge cases:

• Omitting state skips session cleanup, so returning to a previously filtered explore restores old filters despite the documented default-state behavior. The existing test passes state: ""; the equivalent test with state omitted fails. Could we align the behavior/docs and cover canvas last-visited state too?
• history.back()/forward() traverse the tab's joint history, including host-page entries, so iframe-only navigation and a no-op at the initial dashboard aren't guaranteed. Could we track embed navigation boundaries and test initial-dashboard back plus interleaved host navigation? This concern follows the HTML history semantics; I haven't verified it end to end.

1. Fixed to also clear when state is not provided. Also updated to clear canvas state as well.
2. Moved to an in memory history. Has its drawbacks but wont change the navigation of the parent.

Reflecting more on this, asking the users to call window.history.back() is the best solution IMO. This will avoid unnecessary complex code to track urls. This can lead to more issues vs using browser's APIs

agreed..

Closing in favour of just calling window.history.back() will raise a new PR with updates to docs once we get a confirmation from client.